[adm 6] Restore component data and event binding authoring - #210

Closes #121

Parent roadmap: #115

Summary

Restores first-class contextual component binding authoring without moving execution or owning metadata into Studio.

• adds one canonical selected-node surface at /ankh/bindings/:nodeId, separate from Properties;
• adds a contextual Bindings AppBar action beside Properties;
• authors canonical manifest.dataBindings through the existing Studio manifest mutation/persistence path;
• derives bindable props, events, and event payload metadata from ZORA's canonical binding metadata;
• supports literal, state, context, and operation-result property sources;
• supports event bindings to canonical actions and canonical data-source operations;
• presents external and generated operations through one normalized manifest.dataSources operation model;
• derives operation request inputs and response paths from canonical schemas;
• provides authoring diagnostics for missing operation refs/paths/inputs, unavailable actions, unknown props/events, and incompatible schema values;
• keeps the package-neutral authoring model free of React, ZORA implementation imports, Runtime execution code, and duplicate endpoint/event registries.

Ownership

• Contracts remain the owner of serializable binding/action/data-source shapes.
• ZORA remains the owner of which component props/events are bindable and their payload/value metadata.
• Runtime remains the execution owner for property resolution and event dispatch.
• Studio only presents, validates for authoring, mutates, and persists canonical desired state.

No Contracts, Runtime, or ZORA release was required after the owner audit.

Validation

Functional validation on the completed code passed with Bun 1.3.13:

• bun run build ✅
• bun run test ✅
• bun run typecheck ✅
• targeted ADM 6 acceptance set: 23/23 tests ✅

The targeted coverage includes metadata-driven prop/event resolution, all four property source kinds, action and operation event targets, external/generated operation enumeration, request/response schema handling, diagnostics, contextual routing/AppBar behavior, and manifest persistence round-trip.

Per our agreed workflow, the final branch has not had the lint/format/Knip cleanup pass applied yet; that will be done on this PR before final acceptance review.

Merge note

The branch contains transport commits from connector-based implementation. Please use Squash & Merge once final CI and architecture review are green.